@The purpose of these files is to allow you to print the GEOS Kernel from within the SuperDebugger. SuperDebugger is provided with the geoProgrammer package. This, of course, requires that you have a ram expansion unit (REU). GEORAM will not work as it will not work with geoDebugger, sorry GEORAM users.
The program works as such:
1) Simply boot the geoDebugger application and allow it to go into the SuperDebugger mode.
2) Select the file named "universal" and click on open.
3) Issue the command: printer start,end
'start' refers to the starting address in memory where you would like to begin printing. 'end' is the ending address. They can be in hex, bin, or dec (whatever SuperDebugger will recognize).
One of the first things that will happen is the "autoexec" macro will be executed. This will call a routine in the small ML routines. It will load the current printer driver into memory. If your printer driver is not present then you may or may not recieve an error to that effect. If you can't print then make sure you have a copy of your printer driver on the disk.
There is a bug in it. It will not stop printing voluntarily. You must be there to hit the run-stop key. Why not leave off the ending address then? I don't think the command will work at all then. (forgive my ignorance, but it's been awhile since I've used this thing. I've had a printed copy of the GEOS 2.0 kernel for some time now. I'm uploading this as a friend and to promote MORE programming in GEOS!). Anyway, if you find out why it won't stop then contact me via Q-Link as "Roger LL".
This package is a combination of macros and a small ML routine. It is not intended to be used as a permanent option for printing from the SuperDebugger, though it can be adapted to do that with very little effort and very little change to your programs.
Above all get into the GEOS kernel and just STUDY it. It offers some facinating insight into GEOS.
P.S. You may notice that you will NOT be seeing the GEOS kernel as a bunch of ML routines. The .dbg file contains names for all of the kernel routines. They now have a "K" prefix added to them. For instance:
The routine SaveFile is now "KSaveFile". This does not apply to the jump table at $c100 and thru. It still shows the old names (i.e. SaveFile), but the actual routines themselves are named. I have included the source code so that you may reassemble without the new symbols. The new symbols are in the standard GEOSSYM file. Some of the symbols were not resolved as they are called via an indirect jump. You may wish to fill these in yourself. They consist mainly of disk drive routines at $9000 and thru. The new symbols begin on page 18.
(.txt)